Triple
T30228825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galactic Credit Standard |
E768567
|
entity |
| Predicate | notAlwaysAcceptedOn |
P58067
|
FINISHED |
| Object | Outer Rim Territories |
—
|
NE NERFINISHED |
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: Outer Rim Territories | Statement: [Galactic Credit Standard, notAlwaysAcceptedOn, Outer Rim Territories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notAlwaysAcceptedOn Context triple: [Galactic Credit Standard, notAlwaysAcceptedOn, Outer Rim Territories]
-
A.
doesNotAccept
Indicates that one entity refuses, rejects, or is not configured to receive or allow something from another entity.
-
B.
notFullyAdoptedIn
chosen
Indicates that something has not been completely or universally implemented, accepted, or put into practice within a specified context or domain.
-
C.
acceptedIn
Indicates that something has been formally received, approved, or admitted into a particular context, group, or system.
-
D.
mayReject
Indicates that one entity has the authority or option to refuse, decline, or not accept another entity or proposal.
-
E.
notAvailableFor
Indicates that an entity is currently not accessible, usable, or eligible for a particular action, purpose, or association.
- 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_69f2248108208190be60bf1af343ce70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6802486ac8190a936df82f2988383 |
completed | May 2, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:36 p.m.