Triple
T35076436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phoenix Design |
E1012320
|
entity |
| Predicate | clientScope |
P182085
|
FINISHED |
| Object | international brands |
—
|
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: international brands | Statement: [Phoenix Design, clientScope, international brands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clientScope Context triple: [Phoenix Design, clientScope, international brands]
-
A.
participantScope
Indicates the extent, range, or set of participants that are involved in or affected by a given relationship or action.
-
B.
loginScope
Indicates the specific permissions, access range, or contextual boundaries under which a user or system is authenticated during a login session.
-
C.
accessScope
Indicates the extent or boundaries of access that one entity has to another entity or resource.
-
D.
organizationalScope
Indicates the range or extent of responsibility, authority, or applicability that an action, policy, or relationship has within an organization or its sub-units.
-
E.
scopeType
Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
- F. None of above. chosen
Provenance (4 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_69f76dd32c008190853aef6028f60208 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7865b4684819093f95e659522b75e |
completed | May 3, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f78575917481909a3defd6a4c366bd |
completed | May 3, 2026, 5:27 p.m. |
Created at: May 3, 2026, 4:01 p.m.