Triple
T34028113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fomalhaut |
E872564
|
entity |
| Predicate | culturalName |
P185982
|
FINISHED |
| Object | Southern Fish |
—
|
NE NERFINISHED |
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: Southern Fish | Statement: [Fomalhaut, culturalName, Southern Fish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: culturalName Context triple: [Fomalhaut, culturalName, Southern Fish]
-
A.
culturalIdentifier
Indicates that one entity serves as a marker, label, or attribute that identifies or characterizes the cultural affiliation, background, or context of another entity.
-
B.
namedForCulturalRegion
Indicates that something is given a name derived from or honoring a specific cultural region.
-
C.
culturalRegister
Indicates the level or type of formality, style, or social context in which language or behavior is used or appropriate.
-
D.
isGivenNameInCulture
Indicates that a particular given (first) name is used or recognized within a specified culture or cultural context.
-
E.
countrySpecificName
Indicates that an entity has a name or label that is specific to, or used within, a particular country.
- 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_69f349a2527c81909a7cd4bda94d70ad |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: May 1, 2026, 1:51 a.m.