Triple
T1287499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | baiji |
E27467
|
entity |
| Predicate | lastLargeSurvey |
P28097
|
FINISHED |
| Object | 2006 Yangtze River survey |
—
|
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: 2006 Yangtze River survey | Statement: [baiji, lastLargeSurvey, 2006 Yangtze River survey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastLargeSurvey Context triple: [baiji, lastLargeSurvey, 2006 Yangtze River survey]
-
A.
surveyedFor
Indicates that one entity has been examined, questioned, or assessed in order to gather information specifically about another entity or topic.
-
B.
surveyMode
Indicates the method or format by which a survey is administered or conducted (e.g., online, phone, in-person).
-
C.
surveyBand
Indicates that an entity conducts or is associated with a survey using a specific observational band or frequency range.
-
D.
surveyed
Indicates that one entity systematically examined, questioned, or measured another entity or group to gather information or assess a situation.
-
E.
firstRecordedSurveyYear
Indicates the calendar year in which the survey was first conducted or recorded for the entity.
- 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_69a496d4ec448190ad653b2590c46711 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c0d1a5508190b4461df77f560df4 |
completed | March 1, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69a4bee41ca08190b0ad6f7ea40c0b62 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4bfa205ec81909d8170b398345615 |
completed | March 1, 2026, 10:37 p.m. |
Created at: March 1, 2026, 7:51 p.m.