Triple
T17731591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FR-55 |
E442597
|
entity |
| Predicate | hasNumericReference |
P53608
|
FINISHED |
| Object | 55 |
—
|
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: 55 | Statement: [FR-55, hasNumericReference, 55]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumericReference Context triple: [FR-55, hasNumericReference, 55]
-
A.
hasReferences
Indicates that one entity cites, points to, or relies on another entity as a reference or source.
-
B.
hasReferenceID
chosen
Indicates that an entity is associated with a specific reference identifier used to uniquely track or distinguish it.
-
C.
hasCanonicalReference
Indicates that one entity serves as the authoritative or standard reference source for another entity.
-
D.
hasNumberInStructure
Indicates that an entity’s structure includes or contains a specific numerical value or component.
-
E.
hasReferenceURL
Indicates that an entity is associated with a specific web address that serves as a reference or source of additional information about it.
- 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_69d8b9ec79688190b86bdcef85a7b3aa |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e478e69f288190900027641952f198 |
completed | April 19, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69e3cde815e08190881972e2d80d151e |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:08 a.m.