Triple
T4911763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ophiuchus |
E110248
|
entity |
| Predicate | popularDescription |
P59393
|
FINISHED |
| Object | 13th sign of the zodiac |
—
|
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: 13th sign of the zodiac | Statement: [Ophiuchus, popularDescription, 13th sign of the zodiac]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: popularDescription Context triple: [Ophiuchus, popularDescription, 13th sign of the zodiac]
-
A.
popularFor
Indicates that something is widely liked, recognized, or favored specifically because of a particular feature, quality, or use.
-
B.
popularName
Indicates that the object is a commonly used or widely recognized name or nickname for the subject.
-
C.
popularity
Indicates how widely liked, admired, or favored something or someone is by a group of people.
-
D.
popularizedIn
Indicates that something became widely known, accepted, or fashionable within a particular place, time period, or context.
-
E.
popularizedBy
Indicates that something became widely known, accepted, or fashionable as a result of the influence or actions of a particular agent.
- 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_69bd44132b94819088522d92beaadc78 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e9c32148190a940a3733ecd1898 |
completed | March 20, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69bd6c325e188190823836d79934e9bc |
completed | March 20, 2026, 3:48 p.m. |
| PDg | Predicate description generation | batch_69bd6cc228088190849f23b7bd4cf549 |
completed | March 20, 2026, 3:50 p.m. |
Created at: March 20, 2026, 1:29 p.m.