Triple
T36301656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archie |
E893831
|
entity |
| Predicate | belongsToNameCulture |
P99146
|
FINISHED |
| Object | English-language names |
—
|
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: English-language names | Statement: [Archie, belongsToNameCulture, English-language names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToNameCulture Context triple: [Archie, belongsToNameCulture, English-language names]
-
A.
culturalName
Indicates that an entity has a name or designation used specifically within a particular culture or cultural context.
-
B.
isGivenNameInCulture
chosen
Indicates that a particular given (first) name is used or recognized within a specified culture or cultural context.
-
C.
belongsToNamingTradition
Indicates that an entity is associated with or classified under a particular naming tradition or convention.
-
D.
namedForCulturalRegion
Indicates that something is given a name derived from or honoring a specific cultural region.
-
E.
hasCulturalDimensionWith
Indicates that one entity possesses or is associated with a particular cultural dimension in relation to another entity.
- 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_69f76e4c1b248190b10667d0213537fe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ffde9263248190996f970b6cf6e49d |
completed | May 10, 2026, 1:25 a.m. |
| PD | Predicate disambiguation | batch_69ffdd760f1c8190abc6c0c1cd97ba5f |
completed | May 10, 2026, 1:20 a.m. |
Created at: May 3, 2026, 4:09 p.m.