Triple
T361075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TrueBlue |
E7852
|
entity |
| Predicate | statusQualificationMetric |
P12363
|
FINISHED |
| Object | tiles (for newer structure) |
—
|
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: tiles (for newer structure) | Statement: [TrueBlue, statusQualificationMetric, tiles (for newer structure)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusQualificationMetric Context triple: [TrueBlue, statusQualificationMetric, tiles (for newer structure)]
-
A.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
-
B.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
C.
eligibilityLevel
Indicates the degree or tier of qualification an entity has for a given benefit, service, or status.
-
D.
qualificationBadge
Indicates that an entity has been awarded or holds a specific qualification badge signifying a certified skill, status, or achievement.
-
E.
eligibility
Indicates that an entity meets the required conditions or qualifications to participate in, receive, or perform something.
- 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_69a2e7e880008190a6ad7e06e5d03007 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebce64c88190a0a8edcc7095f78b |
completed | Feb. 28, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69a2e95c843c8190b2aba9af6e869ba1 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea2c44408190946267525c88e811 |
completed | Feb. 28, 2026, 1:14 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.