Triple
T3121782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Common |
E65200
|
entity |
| Predicate | previousStageName |
P11166
|
FINISHED |
| Object | Common Sense |
—
|
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: Common Sense | Statement: [Common, previousStageName, Common Sense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousStageName Context triple: [Common, previousStageName, Common Sense]
-
A.
firstStageName
Indicates that one entity is the initial or earliest stage name associated with another entity in a sequence or lifecycle.
-
B.
stageName
Indicates that one entity is the performance or professional name used by another entity.
-
C.
stageNameDerivedFrom
Indicates that an entity’s stage name is derived from, based on, or taken from another specified name or source.
-
D.
predecessorName
chosen
Indicates that the value is the name of an entity that directly precedes another in an ordered sequence or lineage.
-
E.
stageOf
Indicates that one entity represents a particular phase, step, or developmental period within the progression or lifecycle of another entity.
- 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_69ad8580c72481909672d37acf647893 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada52ab05c819088204bbb608c837c |
completed | March 8, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69ad9df455088190940ad04419772dc8 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:04 p.m.