Triple
T16344777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GATT contracting parties |
E396901
|
entity |
| Predicate | hasNumberOfMembersAtEnd |
P45752
|
FINISHED |
| Object | over 120 |
—
|
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: over 120 | Statement: [GATT contracting parties, hasNumberOfMembersAtEnd, over 120]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfMembersAtEnd Context triple: [GATT contracting parties, hasNumberOfMembersAtEnd, over 120]
-
A.
hadNumberOfMembers
chosen
Indicates that an entity possessed or was associated with a specific count of members at a given time or in a given context.
-
B.
hasCurrentNumberOfMembers
Indicates the current count of members associated with a given entity.
-
C.
numberOfMembersDeterminedBy
Indicates that the quantity of members in one entity is defined or constrained by another entity or factor.
-
D.
lastKnownNumberOfMembers
Indicates the most recently recorded count of members associated with an entity.
-
E.
hasExtantMembers
Indicates that the referenced group, category, or lineage currently has living or existing members.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2da0da1808190b6477613a07c7a88 |
completed | April 18, 2026, 1:10 a.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.