Triple
T18773539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heliade (unnamed variants) |
E459074
|
entity |
| Predicate | hasUnspecifiedIndividualNames |
P29734
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Heliade (unnamed variants), hasUnspecifiedIndividualNames, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnspecifiedIndividualNames Context triple: [Heliade (unnamed variants), hasUnspecifiedIndividualNames, true]
-
A.
hasUnknownGivenName
Indicates that the given (first) name of the entity is not known or not specified.
-
B.
hasNoCharactersWithNames
Indicates that the subject entity does not contain any characters for whom explicit names are specified.
-
C.
canReferToMultipleIndividuals
chosen
Indicates that a single reference, term, or identifier may correspond to more than one individual rather than uniquely identifying just one.
-
D.
hasNameGivenTo
Indicates that one entity is the name that has been assigned or given to another entity.
-
E.
hasUnknownFamilyName
Indicates that an entity’s family name is not known or has not been specified.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e593378a4081909cc1b0856fce7d7d |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d1126e4819099607837ed5aadca |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.