Triple
T36775101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ECT |
E908593
|
entity |
| Predicate | usedInGovernmentOperations |
P23524
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [ECT, usedInGovernmentOperations, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInGovernmentOperations Context triple: [ECT, usedInGovernmentOperations, yes]
-
A.
usedInGovernmentIn
chosen
Indicates that something is employed, applied, or functions within the context of a specific government or governmental system.
-
B.
usedGovernmentSystem
Indicates that an entity employed or operated under a particular form or system of government.
-
C.
governmentUseVariant
Indicates that a government employs or applies an alternative or modified form of something (e.g., a policy, standard, or resource) instead of the primary version.
-
D.
openedForGovernmentUse
Indicates that something has been made accessible or available specifically for use by a government or its agencies.
-
E.
underGovernment
Indicates that one entity is subject to the authority, control, or jurisdiction of a particular government.
- 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_69f76e798aa08190ace31098d1b13e9f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff1ba8694481909ceb36f26ca85612 |
completed | May 9, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69ff1b27f0f08190a9e74308c5b3d1ba |
completed | May 9, 2026, 11:31 a.m. |
Created at: May 3, 2026, 4:12 p.m.