Triple
T12371581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FAO Major Fishing Area 41 |
E295013
|
entity |
| Predicate | isNumberedWith |
P37553
|
FINISHED |
| Object | two-digit FAO area code |
—
|
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: two-digit FAO area code | Statement: [FAO Major Fishing Area 41, isNumberedWith, two-digit FAO area code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNumberedWith Context triple: [FAO Major Fishing Area 41, isNumberedWith, two-digit FAO area code]
-
A.
isNumbered
Indicates that an entity has been assigned a specific number or position in an ordered sequence.
-
B.
isNumberedBy
chosen
Indicates that an entity is assigned, identified, or organized by a specific number or numbering scheme.
-
C.
hasSeriesNumber
Indicates that an entity is assigned a specific ordinal or sequence number within a series or ordered set.
-
D.
isNumberedRelativeTo
Indicates that one entity’s numbering or ordinal position is defined or interpreted in relation to another entity.
-
E.
numberingStatus
Indicates the status or condition of an entity’s assigned number or numbering process (e.g., whether it has been numbered, is pending, or has a particular numbering state).
- 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_69d6ab6d8a4081908636601e69ddf262 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d942a2d6e08190a13c7ff89af09354 |
completed | April 10, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69d93ecf6b548190a394b6b56a0c1c68 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:54 p.m.