Triple
T19911944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H. |
E478567
|
entity |
| Predicate | hasNameRepresentation |
P103
|
FINISHED |
| Object | "H." |
—
|
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: "H." | Statement: [H., hasNameRepresentation, "H."]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameRepresentation Context triple: [H., hasNameRepresentation, "H."]
-
A.
nameRepresents
Indicates that a given name stands for, denotes, or is used to identify a particular entity.
-
B.
hasNameCharacteristic
Indicates that an entity possesses a specific quality or attribute related to its name.
-
C.
hasRepresentationIn
chosen
Indicates that one entity is represented, depicted, or encoded within another entity, such as a concept, object, or data structure having a corresponding representation in a specific medium or context.
-
D.
hasNameGivenTo
Indicates that one entity is the name that has been assigned or given to another entity.
-
E.
hasProperName
Indicates that an entity is associated with a specific proper name used to uniquely identify it.
- 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_69d8e520682081909892916424699bd5 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e659908ba88190ae0ee0fbfe4ddf64 |
completed | April 20, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.