Triple
T7663877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Two |
E173577
|
entity |
| Predicate | identificationType |
P78632
|
FINISHED |
| Object | non-personal identifier |
—
|
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: non-personal identifier | Statement: [Army Two, identificationType, non-personal identifier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identificationType Context triple: [Army Two, identificationType, non-personal identifier]
-
A.
ianaIdentifierType
Indicates that one entity specifies the type or category of an IANA (Internet Assigned Numbers Authority) identifier associated with another entity.
-
B.
identifierTypeManaged
Indicates that one entity is responsible for administering or controlling the type or scheme of identifiers used for another entity.
-
C.
identityConcept
Indicates that two concepts are the same in identity, representing exactly the same underlying idea or meaning.
-
D.
credentialType
Indicates the specific kind or category of credential associated with an entity or relationship.
-
E.
typeOfDocumentIssued
Indicates the specific kind or category of document that has been formally issued in a given context.
- 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_69c699562484819086752091e3164a27 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7063dab1881909598b04999b8b690 |
completed | March 27, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69c7015f7430819099d3ea2781b7cee2 |
completed | March 27, 2026, 10:14 p.m. |
| PDg | Predicate description generation | batch_69c7063cfd78819095c6501fe8d57312 |
completed | March 27, 2026, 10:35 p.m. |
Created at: March 27, 2026, 4 p.m.