Triple
T4458137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCPS |
E97781
|
entity |
| Predicate | sharesInformationWith |
P56641
|
FINISHED |
| Object | federal civilian agencies |
—
|
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: federal civilian agencies | Statement: [NCPS, sharesInformationWith, federal civilian agencies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesInformationWith Context triple: [NCPS, sharesInformationWith, federal civilian agencies]
-
A.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
B.
sharesNameWith
Indicates that two entities have the same name or an identical naming designation.
-
C.
sharesIn
Indicates that one entity holds or possesses shares or ownership stakes in another entity.
-
D.
sharesStatusWith
Indicates that two entities have the same status or state within a given context.
-
E.
sharesBaseWith
Indicates that two entities have a common underlying base element, source, or component from which they are derived or constructed.
- F. None of above. chosen
Provenance (4 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_69b3454777808190b78aa9047ba1f018 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3564485688190a0d49fdccf8724be |
completed | March 13, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69b34f649df081909d3cc2f6a1b8f282 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b354e1f0948190b645096b2b7037af |
completed | March 13, 2026, 12:05 a.m. |
Created at: March 12, 2026, 11:33 p.m.