Triple
T23898990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TUS |
E600986
|
entity |
| Predicate | hasUSPortOfEntryStatus |
P7852
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [TUS, hasUSPortOfEntryStatus, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUSPortOfEntryStatus Context triple: [TUS, hasUSPortOfEntryStatus, yes]
-
A.
hasBorderControlStatus
Indicates the type or condition of border control that applies to a given entity or location.
-
B.
legalStatusAtArrival
Indicates the legal status or classification an entity held at the time it first arrived at a particular place or jurisdiction.
-
C.
hasCustomsAndImmigration
chosen
Indicates that customs and immigration control services are present or provided at a given location or facility.
-
D.
illegalityStatusAtDeparture
Indicates whether an entity’s departure from a location or jurisdiction was illegal at the time it occurred.
-
E.
hasBorderControlHistory
Indicates that there is a documented history of actions, policies, or events related to border control involving the associated entities.
- 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_69e295341ac0819080647f2908af793c |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cddca9708190acd3e9edc9b5940b |
completed | April 29, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:25 p.m.