Triple
T18643131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reference.com |
E455737
|
entity |
| Predicate | hasSubjectDomain |
P68688
|
FINISHED |
| Object | general reference |
—
|
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: general reference | Statement: [Reference.com, hasSubjectDomain, general reference]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubjectDomain Context triple: [Reference.com, hasSubjectDomain, general reference]
-
A.
hasPrimarySubject
Indicates that an entity is the main or principal subject associated with another entity or resource.
-
B.
hasTypicalSubject
Indicates that something is commonly or characteristically used as the subject (agent or topic) of a given relation or action.
-
C.
containsDomain
chosen
Indicates that one entity includes or encompasses a specific domain as part of its scope, structure, or area of applicability.
-
D.
hasLegalSubject
Indicates that an entity serves as the legal subject (e.g., rights-holder or obligated party) in a legal relationship or context.
-
E.
hasMainSubjectKey
Indicates that an entity is associated with a primary or principal subject identifier used as its main reference or key.
- 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5500b6d7c8190b807b772980d913c |
completed | April 19, 2026, 9:58 p.m. |
| PD | Predicate disambiguation | batch_69e478d85864819093cbad5ed9b54878 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:47 a.m.