Triple
T18289096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electra 225 |
E438059
|
entity |
| Predicate | typicalCustomerPerception |
P39479
|
FINISHED |
| Object | status symbol |
—
|
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: status symbol | Statement: [Electra 225, typicalCustomerPerception, status symbol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCustomerPerception Context triple: [Electra 225, typicalCustomerPerception, status symbol]
-
A.
influencedPerceptionOf
Indicates that one entity has affected, shaped, or altered how another entity is perceived or understood.
-
B.
typicalInteraction
Indicates the usual or most common way in which two entities interact or relate to each other.
-
C.
hasPublicPerception
chosen
Indicates that an entity is associated with a particular way it is viewed, judged, or regarded by the general public or society.
-
D.
perceivedAttribute
Indicates that one entity recognizes, interprets, or assigns a particular attribute or quality to another entity.
-
E.
customerFocus
Indicates that one entity prioritizes understanding and meeting the needs, preferences, or satisfaction of another entity (typically a customer or client).
- 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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e500fd65888190afdbb29dc60066af |
completed | April 19, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e44fdf43d08190bbcfb6b1fe3cc0ee |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:35 a.m.