Triple
T36530999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brunovistulian terrane |
E900441
|
entity |
| Predicate | hasDeformationAge |
P189532
|
FINISHED |
| Object | Variscan |
—
|
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: Variscan | Statement: [Brunovistulian terrane, hasDeformationAge, Variscan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDeformationAge Context triple: [Brunovistulian terrane, hasDeformationAge, Variscan]
-
A.
hasDeformation
Indicates that one entity exhibits or is characterized by a physical or structural deformation associated with another entity or condition.
-
B.
hasAgeOfOnset
chosen
Indicates the point in time or age at which a condition, event, or state first begins or appears for an entity.
-
C.
hasAgeTransformation
Indicates a relationship where an entity undergoes or causes a change in age or age-related state.
-
D.
hasInternalDeformation
Indicates that one entity exhibits structural distortion or change within its interior caused by stress, force, or other internal factors.
-
E.
hasCharacterAgeIssue
Indicates that there is a problem, inconsistency, or concern related to a character’s age within the given context or data.
- F. None of above.
Provenance (3 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_69f76e5fbb388190b70c4c15573c8143 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff79e7206c8190a809b5f2a6261378 |
completed | May 9, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69ff798356b881908645074fb3a96517 |
completed | May 9, 2026, 6:14 p.m. |
Created at: May 3, 2026, 4:11 p.m.