Triple
T13894883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yahoo homepage |
E334061
|
entity |
| Predicate | requiresAccountForEmail |
P111923
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Yahoo homepage, requiresAccountForEmail, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresAccountForEmail Context triple: [Yahoo homepage, requiresAccountForEmail, true]
-
A.
activationRequirement
Indicates the conditions or prerequisites that must be satisfied for an entity, process, or function to become active or operational.
-
B.
administrationRequired
Indicates that a particular action, process, or resource can only be performed, accessed, or modified when administrative authorization or privileges are present.
-
C.
confirmationRequirement
Indicates that an action, decision, or change is contingent on receiving explicit confirmation from a specified party or process.
-
D.
ordinationRequiredFor
Indicates that a formal ordination is a necessary prerequisite for performing or holding the specified role, function, or office.
-
E.
requiresAccountToWatch
Indicates that accessing or viewing the content is only possible if the user has an account.
- 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_69d81c5dd2d48190b7a5fc1e009de936 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de23a741908190bdf46d76c5f1411a |
completed | April 14, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69dd464b1ab48190ae50bfc902bf6ef7 |
completed | April 13, 2026, 7:38 p.m. |
| PDg | Predicate description generation | batch_69de01ed2098819088ec45069f6f2609 |
completed | April 14, 2026, 8:59 a.m. |
Created at: April 9, 2026, 10:15 p.m.