Triple
T36921924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pola X |
E913225
|
entity |
| Predicate | titleComponentMeaning |
P4542
|
FINISHED |
| Object | Pola stands for Polar |
—
|
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: Pola stands for Polar | Statement: [Pola X, titleComponentMeaning, Pola stands for Polar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleComponentMeaning Context triple: [Pola X, titleComponentMeaning, Pola stands for Polar]
-
A.
titleMeaning
chosen
Indicates that one entity expresses or explains the meaning, significance, or interpretation of another entity’s title.
-
B.
titleComponent
Indicates that one entity is a component or segment of the overall title associated with another entity.
-
C.
titleLanguageMeaning
Indicates that a title is expressed in a particular language and conveys a specific meaning in that language.
-
D.
titleKey
Indicates that one entity serves as a key or identifier used to reference or retrieve the title associated with another entity.
-
E.
meaningComponent
Indicates that one entity represents a semantic or conceptual component contributing to the overall meaning 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_69f76e885b848190bad82c87e9525486 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffc605b0648190a7abe9128b0d857a |
completed | May 9, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69ffc5742d80819099f947ece78d5700 |
completed | May 9, 2026, 11:38 p.m. |
Created at: May 3, 2026, 4:13 p.m.