Triple
T14392298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metapatterns: Across Space, Time, and Mind |
E356873
|
entity |
| Predicate | hasMetapattern |
P114067
|
FINISHED |
| Object | spheres |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: spheres | Statement: [Metapatterns: Across Space, Time, and Mind, hasMetapattern, spheres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMetapattern Context triple: [Metapatterns: Across Space, Time, and Mind, hasMetapattern, spheres]
-
A.
hasMetaSubject
Indicates that an entity is associated with a subject at a meta-level, such as the topic, theme, or aboutness of the entity rather than its direct content or participants.
-
B.
hasMet
Indicates that one entity has encountered or come into contact with another entity at least once.
-
C.
hasPattern
Indicates that one entity exhibits, follows, or is characterized by a specific recurring form, structure, or design defined by another entity.
-
D.
hasUsePattern
Indicates a characteristic or recurring way in which something is typically used or applied.
-
E.
hasPlanningPattern
Indicates that an entity follows or is associated with a particular planning pattern or structured approach to planning.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de902b9acc8190817ffa848a76a880 |
completed | April 14, 2026, 7:06 p.m. |
| PD | Predicate disambiguation | batch_69de2aa024c48190805df6a9d63deb10 |
completed | April 14, 2026, 11:53 a.m. |
| PDg | Predicate description generation | batch_69de2e08b6c08190bb4c929deab236a6 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:16 a.m.