Triple
T930821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trafficking in Persons Report |
E20087
|
entity |
| Predicate | tierSystem |
P16816
|
FINISHED |
| Object | Tier 1 |
—
|
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: Tier 1 | Statement: [Trafficking in Persons Report, tierSystem, Tier 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tierSystem Context triple: [Trafficking in Persons Report, tierSystem, Tier 1]
-
A.
ratingSystem
chosen
Indicates a system or method used to assign evaluative scores or rankings to items, actions, or entities based on defined criteria.
-
B.
thirdTier
Indicates that an entity occupies a third level or rank within a hierarchical structure or classification.
-
C.
titleSystem
Indicates that a system assigns or holds a formal title or designation for an entity.
-
D.
marginSystem
Indicates a financial arrangement where securities are bought or held using borrowed funds, with the securities themselves serving as collateral under a defined margin framework.
-
E.
tiebreaker
Indicates that one entity serves as the deciding factor used to break a tie between two or more otherwise equal options or outcomes.
- 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_69a493af3dc48190adb7263e6e445ea1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b34b302c81908fa32cb18f551493 |
completed | March 1, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69a4b29876348190a29f4ff9878074a5 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.