Triple
T1810052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australorp |
E40310
|
entity |
| Predicate | recordEggProductionPerYear |
P7997
|
FINISHED |
| Object | 364 eggs in 365 days |
—
|
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: 364 eggs in 365 days | Statement: [Australorp, recordEggProductionPerYear, 364 eggs in 365 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordEggProductionPerYear Context triple: [Australorp, recordEggProductionPerYear, 364 eggs in 365 days]
-
A.
eggType
Indicates the specific category or kind of egg associated with an entity (e.g., its classification or type).
-
B.
eggStorageRequirement
Indicates the specific conditions or methods required for properly storing eggs.
-
C.
totalProduction
chosen
Indicates the overall quantity of goods, services, or output produced by an entity or system over a specified period or within a defined scope.
-
D.
year
Indicates the specific calendar year associated with an entity, event, or fact.
-
E.
increasesProductionOf
Indicates that one entity causes a rise or enhancement in the amount or rate at which another entity is produced.
- 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_69a88643a3388190a612f2ebe1fb29e7 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab694d75ac8190a4d61399c04b9fb9 |
completed | March 6, 2026, 11:54 p.m. |
| PD | Predicate disambiguation | batch_69aa61d6b8ec8190a1597b2e44ea6534 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:32 p.m.