Triple
T24430984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commander Shepard |
E616000
|
entity |
| Predicate | customizableAttributes |
P139067
|
FINISHED |
| Object | appearance |
—
|
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: appearance | Statement: [Commander Shepard, customizableAttributes, appearance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: customizableAttributes Context triple: [Commander Shepard, customizableAttributes, appearance]
-
A.
customizableBy
Indicates that one entity can be modified, configured, or tailored in some way by another entity.
-
B.
customizableWith
Indicates that one entity can be modified, configured, or tailored in some way using another entity.
-
C.
customizableFeatures
chosen
Indicates that certain aspects or options of an entity can be modified or configured according to specific preferences or requirements.
-
D.
commonAttribute
Indicates that two or more entities share the same specified attribute or property.
-
E.
custom
Indicates that something is specially created, configured, or tailored for a particular purpose, context, or user rather than being standard or generic.
- 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_69e2d7eadb248190a867130fe45f0388 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29782a4a0819087cb7ba399371520 |
completed | April 29, 2026, 11:42 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:16 a.m.