Triple
T33719916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tenderfoot rank |
E863980
|
entity |
| Predicate | requiresBoardOfReview |
P108090
|
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: [Tenderfoot rank, requiresBoardOfReview, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresBoardOfReview Context triple: [Tenderfoot rank, requiresBoardOfReview, yes]
-
A.
requiresManagementBoard
Indicates that something must be overseen, approved, or governed by a management board in order to proceed or be valid.
-
B.
requiresAssessmentBy
chosen
Indicates that one entity must be formally evaluated, reviewed, or judged by another specified entity before proceeding or being accepted.
-
C.
requiresAdviceAndApprovalOf
Indicates that one entity can proceed with an action or decision only if it first seeks guidance and obtains formal approval from another entity.
-
D.
reviewedBy
Indicates that an item, work, or action has been examined and evaluated by a specific agent or reviewer.
-
E.
requiresAssessmentOf
Indicates that one entity necessitates an evaluation, review, or judgment to be performed on another entity before proceeding or fulfilling a condition.
- 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_69f34989871c81908682e22a2fe4b829 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff4de66ba481908e7184b3cf9d4d2d |
completed | May 9, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69ff4c702a5881909c6684c74807e945 |
completed | May 9, 2026, 3:02 p.m. |
Created at: May 1, 2026, 1:44 a.m.