Triple
T32234871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rufe |
E823440
|
entity |
| Predicate | hasReportingNameType |
P203768
|
FINISHED |
| Object | Allied reporting name |
—
|
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: Allied reporting name | Statement: [Rufe, hasReportingNameType, Allied reporting name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReportingNameType Context triple: [Rufe, hasReportingNameType, Allied reporting name]
-
A.
supportsNameType
Indicates that one entity is capable of handling, recognizing, or being associated with a particular type or category of name.
-
B.
hasTypeName
Indicates that an entity is associated with a specific type name used to classify or identify its kind.
-
C.
hasNameElementType
Indicates that something includes a specific type or category of element within its name.
-
D.
hasRegistrationType
Indicates that an entity is associated with a specific category or type of registration it holds or requires.
-
E.
hasNameOriginType
Indicates that there is a specific type or category describing the origin of an entity’s name.
- 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_69f3490c140481908ed53b98b561eaa1 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a01ed1790148190b08c1dba53de4371 |
completed | May 11, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_6a01e9c20798819085760b377dc7b3fa |
completed | May 11, 2026, 2:37 p.m. |
| PDg | Predicate description generation | batch_6a01ed16dfe88190a030c75107b954a5 |
completed | May 11, 2026, 2:52 p.m. |
Created at: May 1, 2026, 12:39 a.m.