Triple
T10924109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TCA |
E258020
|
entity |
| Predicate | hasCodeCategory |
P51031
|
FINISHED |
| Object | country and territory 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: country and territory code | Statement: [TCA, hasCodeCategory, country and territory code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCodeCategory Context triple: [TCA, hasCodeCategory, country and territory code]
-
A.
haveCategoryCode
chosen
Indicates that an entity is associated with a specific classification or category identified by a code.
-
B.
hasCodeIn
Indicates that one entity is represented, defined, or implemented within the codebase or coding context of another entity.
-
C.
hasFunctionCategory
Indicates that something is associated with a particular functional category or role it performs.
-
D.
hasCodeName
Indicates that an entity is known or referred to by a particular alternative name or alias, often used for secrecy or distinction.
-
E.
hasTypeCode
Indicates that an entity is associated with a specific type classification represented by a code.
- 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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7708f7ab48190b60a4bb8fdb17c8e |
completed | April 9, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69d72e799f808190b6ab64fc7586a303 |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:22 p.m.